24 Apr - 14 Aug, 2020 Schedule Published

Welcome to PyCon India 2020 CFP

The major change this year is the online format of the Conference.

There are 2 categories of Proposals - Talks and Workshops. You can select the category from the 'Proposal Type' Dropdown in the Proposal Submission Page. Here is a brief overview of both Categories.

Talks

Technical talks are the most important event at PyCon India, the core of the conference essentially. Two of the four days are dedicated to talks. Talks are short lectures (25 min slot) supported by a presentation. Speakers come from the Python community.

This year we have introduced a preview video section where you need to add a short preview video mentioning the overview of the Talk. To know read the CFP announcement blog post

Talks are selected through a CFP (Call For Proposals) process. Interested members of the community propose their talks. An editorial panel designated by the organisers makes the selections. The 2019 edition of the conference saw some 303 proposals, of which 36 were selected.

CFP applications from the previous years can be seen here.

Important Points

• There are three parallel tracks
• Talk duration is __30__ mins (25 mins for the talk, 5 mins - Q&A)
• CFP closes on 14th August 2020
• Schedule shall be released on 1st September 2020
• Talks will be presented on 2nd and 3rd October 2020

Workshops

Workshops are an important part of the PyCon India. Hands on learning is as important as talks for a fulfilling conference experience. Like talks, workshops are also conducted by the members of the Python community.

Anyone can propose for conducting a workshop. Any topic of interest to the Python community is okay - the workshop should help attendees learn a new skill, technology or library. To get a sense of the topics from last year, take a look here.

In the CFP proposal, please mention an outline of the workshop and the prerequisites. And the slides if possible. Also mention if you have conducted the same workshop before.

The workshop should be interspersed with proper hands-on exercises. After the workshop people should be ramped up on the workshop topic, and should be able to take it forward themselves.

To know about Best practices please check the Workshop Proposal Announcement blog post.

Important Points

• Workshop duration is 2.5 hours (A small break in between as planned by the speaker)
• CFP closes on 31st August 2020
• Schedule shall be released on 15th September 2020
• Workshops will be conducted on 4th October 2020

What to Propose

Anything of interest to Python programmers is welcome. However, there are a few topics that we feel might be great -

• Lessons from using Python in your project. Did you find something against conventional wisdom? Something confirming conventional wisdom ? Do you have advise for people solving similar problems? Example - I tried Python for video processing, or in my medical imaging project, and here are the lessons.
• Something you're doing to make the language/ecosystem better. Writing a library to solve an interesting problem ? Or have some new ideas on optimisation.
• Something you learned from a different language that may be useful to Python community. How about a type system? Or patterns from functional programming. Or logic programming maybe?
• Thoughts on tech culture and living. Ideas on improving diversity and inclusiveness. On programmers’ physical and mental health. On getting better at productivity. On workplace issues. Anything that can make an impact, especially if you have used Python for any of the above or have seen someone using Python.

And if you don't get any ideas along these lines, try plain and simple teaching. Pick up an niche topic (maybe a recent technology, or a scientific paper), and help us learn. A well delivered lecture even at a beginner level is often well received.

The Review Process

• Authors should propose their talks using the CFP application
• CFP volunteers review the proposals for completeness
• Once the proposals are ready, they are be reviewed by a panel of experts
• If the proposal does not look complete, or the reviewers need clarifications, the author is notified via comments
• The panel of experts finally vote on the proposals
• A pre-final shortlist is eventually prepared based on the votes
• The shortlisted proposals go through a round of rehearsals (more details in section below)
• A final list is created and published.

Rehearsals

Shortlisted speakers will be expected to participate in rehearsal sessions. Rehearsals will be done via teleconferencing, where the speaker shall give a mock run of their talks in a time-bound manner. The audience will consist of volunteers, reviewers and possibly other speakers. The speakers will be given feedback if necessary.

The point of this exercise is to make sure speakers are ready with their talks ahead of time. And also, to make sure they can finish the talk in the stipulated time. It is useful for the speakers too as they'd get feedback on the content delivery and presentation.

Participation in the rehearsal sessions is likely to be a required step - chances of an unrehearsed talk making it to the final stage are substantially lower.

Diversity

We in the Python community believe in making our community more diverse. This means we are encouraging content from diverse walks of life. This also means we want to improve participation from under-represented groups.

Our goal is to maximise content from under-represented groups. You can help us by encouraging your friends, family and colleagues to submit talks. You can also help by mentoring.

Also note that we have a strict code-of-conduct. This is to make it clear, in intent and practice, that we are committed to making the conference a pleasant, welcoming and harassment free experience for everyone, especially for under-represented groups.

Best Practices for Speakers

1. Apply

Even if you have a vague idea, submit a proposal. We're available for help with ideas and feedback (contact information is in the section below). Don't worry about communication skills or English - we are there to help with that too. And our focus is more on the content.

2. Make it detailed

Add as much detail as possible to the proposal. Add the presentation slides if you already have one. Add a short minute video giving a summary of the proposal. More detail helps reviewers make better judgement.

3. Propose early

We will start the review process as the proposals come in, and not at the end. Proposals submitted early will get more attention and feedback

4. The code of conduct

Take a look at the code of conduct, and be mindful of it. The gist is, be nice and avoid using sexist language.

5. Add a preview video

Add a small intro video about what your talk is about to provide a preview to what's to be expected.

We've put together a set of detailed best practices - take a look. It also contains links to some well written proposals from previous years.

Questions and Discussions

Ping us on Zulip or IRC (#pyconindia) Or contact the coordinators through email:

Anirudha - anirudhastark@gmail.com

Ritesh - udr.ritesh@gmail.com

The team: cfp@in.pycon.org